-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
[V1][Draft] Jump-forward decoding #15490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[V1][Draft] Jump-forward decoding #15490
Conversation
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
Will ping once it is ready, discussing with Yixin atm to clear up some confusion |
This pull request has merge conflicts that must be resolved before it can be |
a1048e6
to
236830d
Compare
Signed-off-by: Aaron Pham <[email protected]>
Signed-off-by: Aaron Pham <[email protected]>
236830d
to
a97b172
Compare
This pull request has merge conflicts that must be resolved before it can be |
This PR aims to add support for jump-forward decoding by introducing the following API:
Grammar
class:jump_forward_string
: returns the longest jf-able string from the FSMfind_token_divergence
: returns the index of shared outputs ids between (prev_output) and (prev_output+jf_string) and handle FSM accordingly--wip--
Signed-off-by: Aaron Pham [email protected]